Skip to content

MON-4357: Bump API version to include Monitoring capability #9925

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Draft
rexagod wants to merge 1 commit into
base: main
Choose a base branch
from
Draft

MON-4357: Bump API version to include Monitoring capability #9925

rexagod wants to merge 1 commit into from

Conversation

@rexagod
Copy link
Member

@rexagod rexagod commented Sep 3, 2025 •
edited
Loading

Bump API version to include "Monitoring" capability in Installer so it doesn't get rejected.

Blocked by: https://github.com/openshift/api/pull/2468/files

@rexagod
MON-X: Bump API version to include Monitoring capability
2ad4f1d 
Bump API version to include "Monitoring" capability in Installer so it
doesn't get rejected.

Signed-off-by: Pranshu Srivastava <[email protected]>
@rexagod rexagod marked this pull request as draft September 3, 2025 22:59
@openshift-ci openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Sep 3, 2025
@openshift-ci openshift-ci bot requested review from jhixson74 and tthvo September 3, 2025 23:00
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Sep 3, 2025

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign andfasano for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@rexagod rexagod changed the title MON-X: Bump API version to include Monitoring capability MON-4357: Bump API version to include Monitoring capability Sep 3, 2025
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Sep 3, 2025 •
edited by openshift-ci bot
Loading

@rexagod: This pull request references MON-4357 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the task to target the "4.21.0" version, but no target version was set.

Details

In response to this:

Bump API version to include "Monitoring" capability in Installer so it doesn't get rejected.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Sep 3, 2025
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Sep 11, 2025

@rexagod: all tests passed!

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Sep 18, 2025 •
edited by openshift-ci bot
Loading

@rexagod: This pull request references MON-4357 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the task to target the "4.21.0" version, but no target version was set.

Details

In response to this:

Bump API version to include "Monitoring" capability in Installer so it doesn't get rejected.

Blocked by: https://github.com/openshift/api/pull/2468/files

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@rexagod rexagod mentioned this pull request Sep 18, 2025
Draft
@openshift-bot
Copy link
Contributor

openshift-bot commented Dec 18, 2025

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@openshift-ci openshift-ci bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Dec 18, 2025
@openshift-merge-robot openshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Dec 18, 2025
@openshift-merge-robot
Copy link
Contributor

openshift-merge-robot commented Dec 18, 2025

PR needs rebase.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@openshift-bot
Copy link
Contributor

openshift-bot commented Jan 17, 2026

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

@openshift-ci openshift-ci bot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Jan 17, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@jhixson74 jhixson74 Awaiting requested review from jhixson74

@tthvo tthvo Awaiting requested review from tthvo

Assignees

No one assigned

Labels

do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD.

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

4 participants

@rexagod @openshift-ci-robot @openshift-bot @openshift-merge-robot